Optimizing loading of web page based on aggregated user preferences for web page elements of web page

ABSTRACT

A method, system and computer program product for optimizing the loading of a web page. The server receives indications (e.g., Document Object Model (DOM) elements) of web page elements of interest of a web page from multiple client devices. The server updates a list of web page elements for the requested web page that is sorted in terms of popularity based on these received indications of web page elements of interest. The server may then appropriately respond to a request to retrieve that web page by accessing such a list and transmitting to the browser of the requesting client device the data to populate the content of the web page elements for the requested web page in an order based on the sorted list. In this manner, the browser will be able to optimize the loading of the web page.

TECHNICAL FIELD

The present invention relates generally to web pages, and moreparticularly to optimizing the loading of a web page based on theaggregated user preferences for the web page elements of the web page.

BACKGROUND

A web page is a web document or other web resource that is suitable forthe World Wide Web and can be accessed through a web browser anddisplayed on a user's computing device display. Web pages may beretrieved by the web browser from a remote server, commonly referred toas a “web server.” The retrieved web page may in the form of a HyperTextMarkup Language (HTML) document, which is read and parsed by thebrowser, such as into the “Document Object Model” tree structure. Thebrowser then loads the elements of the web page (e.g., images) from theweb server, such as based on the order that the elements appear in theHTML document. As a result, the user may have to wait for the entire webpage to be loaded before the user can see the information they areinterested in the web page. For example, when the user accesses awebsite for a local news television station, the user may only beinterested in viewing information regarding the weather and local news.However, the user may have to wait for the entire web page to be loadedbefore they can view the information regarding the weather and localnews if these elements are loaded last.

Such a problem is compounded by mobile computing devices, which haveslower processing speeds and less memory thereby taking longer todownload a web page from a web server and increasing the length of timein which the user may have to wait to view the information of interest.

As a result, the current means for loading a web page may cause the userto wait for the entire web page to be loaded, which can be a significantamount of time depending on the connection speed, prior to viewing theinformation of interest.

SUMMARY

In one embodiment of the present invention, a method for optimizing theloading of a web page comprises receiving a request to retrieve a webpage from a computing device of a user. The method further comprisesaccessing a list of web page elements for the requested web page that issorted in terms of popularity. The method additionally comprisestransmitting data to the computing device of the user to populatecontent of the web page elements of the requested web page in an orderbased on the sorted list.

Other forms of the embodiment of the method described above are in asystem and in a computer program product.

The foregoing has outlined rather generally the features and technicaladvantages of one or more embodiments of the present invention in orderthat the detailed description of the present invention that follows maybe better understood. Additional features and advantages of the presentinvention will be described hereinafter which may form the subject ofthe claims of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained when thefollowing detailed description is considered in conjunction with thefollowing drawings, in which:

FIG. 1 illustrates a network system configured in accordance with anembodiment of the present invention;

FIG. 2 illustrates a hardware configuration of a client device inaccordance with an embodiment of the present invention;

FIG. 3 illustrates a hardware configuration of a server in accordancewith an embodiment of the present invention;

FIG. 4 is a flowchart of a method for optimizing the loading of a webpage in accordance with an embodiment of the present invention;

FIG. 5 is a flowchart of a method for retrieving a web page, where theuser had previously expressed an interest in an element(s) on that webpage in accordance with an embodiment of the present invention;

FIG. 6 is a flowchart of a method for retrieving a web page when theuser concurrently expresses an element(s) of interest along with therequest to retrieve a web page in accordance with an embodiment of thepresent invention; and

FIG. 7 is a flowchart of a method for retrieving a web page when theuser does not express an element of interest for the requested web pagein accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention comprises a method, system and computer programproduct for optimizing the loading of a web page. In one embodiment ofthe present invention, the server receives indications (e.g., DocumentObject Model (DOM) elements) of web page elements of interest of a webpage from multiple client devices. The server updates a list of web pageelements for the requested web page that is sorted in terms ofpopularity based on these received indications of web page elements ofinterest. Upon establishing a list that reflects the most requested webpage elements for the web page, the server may appropriately respond toa request to retrieve the web page by accessing such a list andtransmitting to the browser of the requesting client device the data topopulate the content of the web page elements for the requested web pagein an order based on the sorted list. In this manner, the server will beable to transmit to the browser of the requesting client device the datato populate the content of the elements of the requested web page thatare higher in interest prior to those of lower in interest therebyoptimizing the loading of the web page (i.e., possibly reducing thewaiting time for the user to view the element(s) of interest in therequested web page).

In the following description, numerous specific details are set forth toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details. In other instances,well-known circuits have been shown in block diagram form in order notto obscure the present invention in unnecessary detail. For the mostpart, details considering timing considerations and the like have beenomitted inasmuch as such details are not necessary to obtain a completeunderstanding of the present invention and are within the skills ofpersons of ordinary skill in the relevant art.

Referring now to the Figures in detail, FIG. 1 illustrates a networksystem 100 for practicing the principles of the present invention inaccordance with an embodiment of the present invention. Network system100 includes client devices 101A-101C (identified as “Client Device A,”“Client Device B,” and “Client Device C,” respectively, in FIG. 1)connected to a server 102 via a network 103. Client devices 101A-101Cmay collectively or individually be referred to as client devices 101 orclient device 101, respectively. Client device 101 may be any type ofcomputing device (e.g., portable computing unit, Personal DigitalAssistant (PDA), smartphone, laptop computer, mobile phone, navigationdevice, game console, desktop computer system, workstation, Internetappliance and the like) configured with the capability of connecting tonetwork 103 and consequently communicating with other client devices 101and server 102. A description of the hardware configuration of client101 is provided below in connection with FIG. 2.

In one embodiment, server 102 may be a web server configured to hostwebsites. In one embodiment, server 102 is configured to transmit thedata to populate the content of the elements of a web page to a browserof client device 101 in a particular order based on the relativepriority of the elements of the web page as discussed further herein. Adescription of the hardware configuration of server 102 is providedbelow in connection with FIG. 3.

Network 103 may be, for example, a local area network, a wide areanetwork, a wireless wide area network, a circuit-switched telephonenetwork, a Global System for Mobile Communications (GSM) network,Wireless Application Protocol (WAP) network, a WiFi network, an IEEE802.11 standards network, various combinations thereof, etc. Othernetworks, whose descriptions are omitted here for brevity, may also beused in conjunction with system 100 of FIG. 1 without departing from thescope of the present invention.

While FIG. 1 illustrates three clients 101A-101C and a single server102, network system 100 may include any number of clients 101 andservers 102. The embodiments of network system 100 are not to be limitedin scope to the depiction of FIG. 1.

Referring now to FIG. 2, FIG. 2 illustrates a hardware configuration ofclient 101 (FIG. 1) which is representative of a hardware environmentfor practicing the present invention. Referring to FIG. 2, client 101has a processor 201 coupled to various other components by system bus202. An operating system 203 runs on processor 201 and provides controland coordinates the functions of the various components of FIG. 2. Anapplication 204 in accordance with the principles of the presentinvention runs in conjunction with operating system 203 and providescalls to operating system 203 where the calls implement the variousfunctions or services to be performed by application 204. Application204 may include, for example, a web browser.

Referring again to FIG. 2, read-only memory (“ROM”) 205 is coupled tosystem bus 202 and includes a basic input/output system (“BIOS”) thatcontrols certain basic functions of client 101. Random access memory(“RAM”) 206 and disk adapter 207 are also coupled to system bus 202. Itshould be noted that software components including operating system 203and application 204 may be loaded into RAM 206, which may be client's101 main memory for execution. Disk adapter 207 may be an integrateddrive electronics (“IDE”) adapter that communicates with a disk unit208, e.g., disk drive.

Client 101 may further include a communications adapter 209 coupled tobus 202. Communications adapter 209 interconnects bus 202 with anoutside network (e.g., network 103 of FIG. 1) thereby enabling client101 to communicate with other clients 101 and server 102.

I/O devices may also be connected to client 101 via a user interfaceadapter 210 and a display adapter 211. Keyboard 212, mouse 213 andspeaker 214 may all be interconnected to bus 202 through user interfaceadapter 210. A display monitor 215 may be connected to system bus 202 bydisplay adapter 211. In this manner, a user is capable of inputting toclient 101 through keyboard 212 or mouse 213 and receiving output fromclient 101 via display 215 or speaker 214.

Referring now to FIG. 3, FIG. 3 illustrates a hardware configuration ofserver 102 (FIG. 1) which is representative of a hardware environmentfor practicing the present invention. Server 102 has a processor 301coupled to various other components by system bus 302. An operatingsystem 303 runs on processor 301 and provides control and coordinatesthe functions of the various components of FIG. 3. An application 304 inaccordance with the principles of the present invention runs inconjunction with operating system 303 and provides calls to operatingsystem 303 where the calls implement the various functions or servicesto be performed by application 304. Application 304 may include, forexample, a program for optimizing the loading of a web page as discussedfurther below in association with FIGS. 4-7.

Referring again to FIG. 3, read-only memory (“ROM”) 305 is coupled tosystem bus 302 and includes a basic input/output system (“BIOS”) thatcontrols certain basic functions of server 102. Random access memory(“RAM”) 306 and disk adapter 307 are also coupled to system bus 302. Itshould be noted that software components including operating system 303and application 304 may be loaded into RAM 306, which may be server's102 main memory for execution. Disk adapter 307 may be an integrateddrive electronics (“IDE”) adapter that communicates with a disk unit308, e.g., disk drive. It is noted that the program for optimizing theloading of a web page, as discussed further below in association withFIGS. 4-7, may reside in disk unit 308 or in application 304.

Server 102 may further include a communications adapter 309 coupled tobus 302. Communications adapter 309 interconnects bus 302 with anoutside network (e.g., network 103 of FIG. 1) thereby enabling server102 to communicate with client 101 (FIG. 1).

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a computer, or other programmable data processing apparatusto produce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks. These computerreadable program instructions may also be stored in a computer readablestorage medium that can direct a computer, a programmable dataprocessing apparatus, and/or other devices to function in a particularmanner, such that the computer readable storage medium havinginstructions stored therein comprises an article of manufactureincluding instructions which implement aspects of the function/actspecified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be accomplished as one step, executed concurrently,substantially concurrently, in a partially or wholly temporallyoverlapping manner, or the blocks may sometimes be executed in thereverse order, depending upon the functionality involved. It will alsobe noted that each block of the block diagrams and/or flowchartillustration, and combinations of blocks in the block diagrams and/orflowchart illustration, can be implemented by special purposehardware-based systems that perform the specified functions or acts orcarry out combinations of special purpose hardware and computerinstructions.

As stated in the Background section, a web page is a web document orother web resource that is suitable for the World Wide Web and can beaccessed through a web browser and displayed on a user's computingdevice display. Web pages may be retrieved by the web browser from aremote server, commonly referred to as a “web server.” The retrieved webpage may in the form of a HyperText Markup Language (HTML) document,which is read and parsed by the browser, such as into the “DocumentObject Model” tree structure. The browser then loads the elements of theweb page (e.g., images) from the web server, such as based on the orderthat the elements appear in the HTML document. As a result, the user mayhave to wait for the entire web page to be loaded before the user cansee the information they are interested in the web page. For example,when the user accesses a website for a local news television station,the user may only be interested in viewing information regarding theweather and local news. However, the user may have to wait for theentire web page to be loaded before they can view the informationregarding the weather and local news if these elements are loaded last.Such a problem is compounded by mobile computing devices, which haveslower processing speeds and less memory thereby taking longer todownload a web page from a web server and increasing the length of timein which the user may have to wait to view the information of interest.As a result, the current means for loading a web page may cause the userto wait for the entire web page to be loaded, which can be a significantamount of time depending on the connection speed, prior to viewing theinformation of interest.

The principles of the present invention provide a means for loadingelements of a web page based on the relative priority of the elements ofthe web page thereby loading elements of interest prior to elements ofnon-interest as discussed further below in connection with FIGS. 4-7.FIG. 4 is a flowchart of a method for optimizing the loading of a webpage. FIG. 5 is a flowchart of a method for retrieving a web page, wherethe user had previously expressed an interest in an element(s) on thatweb page. FIG. 6 is a flowchart of a method for retrieving a web pagewhen the user concurrently expresses an element(s) of interest alongwith the request to retrieve a web page. FIG. 7 is a flowchart of amethod for retrieving a web page when the user does not express anelement of interest for the requested web page.

As stated above, FIG. 4 is a flowchart of a method 400 for optimizingthe loading of a web page in accordance with an embodiment of thepresent invention.

Referring to FIG. 4, in conjunction with FIGS. 1-3, in step 401, server102 receives a request from client device 101 to retrieve a web page.For example, client device 101 may initially receive a request toretrieve a web page from server 102 from the user of client device 101.For instance, the user may type in the Uniform Resource Identifier (URL)in the browser corresponding to the web page to be retrieved from server102. Client device 101 may then send the request to server 102 toretrieve the requested web page.

In step 402, server 102 begins to transmit the data to populate thecontent of the elements of the requested web page asynchronously to therequesting client device 101. The browser of client device 101 will thenstart displaying these elements on display 215 as they are received fromserver 102.

In step 403, the browser of client device 101 receives feedback from theuser of client 101 regarding an interest in a particular element on therequested web page displayed on display 215. For example, the user mayindicate an element of interest in the requested web page by selectingan area on the web page. For instance, the user may draw an outlinearound the element of interest on the web page.

In step 404, the browser of client device 101 identifies the DocumentObject Model (DOM) element of the DOM tree structure for the requestedweb page that corresponds to the user's element of interest on the webpage. That is, the browser identifies the DOM element that correspondsto the element of interest on the web page that was expressed by theuser in step 403.

In step 405, the browser of client device 101 stores the DOM element(e.g., caches the DOM element in a local cache, such as a cache inmemory 206) for later retrieval as discussed further below in connectionwith FIG. 5.

In step 406, the browser of client device 101 transmits an indication(e.g., DOM element) that corresponds to the user's element of intereston the web page to server 102. In one embodiment, client device 101utilizes an Asynchronous Module Definition (AMD) Application ProgrammingInterface (API) to communicate with server 102 for defining web pageelements of interest and their children that can be asynchronouslyloaded as discussed below.

In step 407, server 102 receives the indication (e.g., DOM element) thatcorresponds to the user's element of interest on the web page.

In step 408, server 102 transmits the data (e.g., dynamic data, such asa YouTube® video) to populate the content of the received DOM element aswell as transmits the data to populate the content of the children ofthe received DOM element to client device 101.

In step 409, server 102 transmits the data to populate the content ofthe remaining elements of the web page asynchronously to the requestingclient device 101. That is, server 102 transmits the data to populatethe content of the remaining DOM elements (and their children) of theDOM tree structure asynchronously to the requesting client device 101for the requested web page.

In step 410, server 102 updates a list of web page elements for therequesting web page that is sorted in terms of popularity based on thereceived indication (e.g., DOM element) of a web page element ofinterest (indication received in step 407) from that user as well asindications received from other users as discussed further below. Thatis, server 102 updates a list of web page elements for the requestingweb page that is sorted based on a number of received DOM elements(corresponding to the users' elements of interest on the web page) foreach element on the web page. In one embodiment, such a list is storedin a data storage unit (e.g., memory 306, disk unit 308). In thismanner, server 102 maintains a record for the most requested web pageelements for that web page. Such a record may be dynamically updatedbased on the response from other users as discussed below in connectionwith step 411. As a result, server 102 will be able to transmit to thebrowser of client device 101 the data to populate the content of theelements of the requested web page based on the relative priority of theelements of the web page as discussed further below in connection withFIG. 7.

The above process (steps 401-410) may be repeated in order for server102 to obtain additional feedback from other users concerning elementsof interest on a web page. By obtaining additional feedback from otherusers concerning elements of interest on a web page, server 102 will beable to develop a list, which could be in the form of a map, that sortsor identifies elements of interest in the web page based on users'expressed interest for various elements on the web page. In this manner,server 102 will be able to transmit to the browser of client device 101the data to populate the content of the elements of the requested webpage to be loaded by the browser that are higher in interest prior tothose of lower in interest thereby optimizing the loading of the webpage (i.e., possibly reducing the waiting time for the user to view theelement(s) of interest in the requested web page).

Referring to step 411, a determination is made by server 102 as towhether there are any more requests for the web page. If there isanother request for the web page, then server 102 receives a requestfrom client device 101 to retrieve the web page in step 401.

If, however, server 102 does not receive a request for the web page,then, server 102 continues to monitor for additional requests for theweb page in step 411.

In some implementations, method 400 may include other and/or additionalsteps that, for clarity, are not depicted. Further, in someimplementations, method 400 may be executed in a different orderpresented and that the order presented in the discussion of FIG. 4 isillustrative. Additionally, in some implementations, certain steps inmethod 400 may be executed in a substantially simultaneous manner or maybe omitted.

As discussed above, in connection with method 400, the browser of clientdevice 101 may store the DOM element (e.g., caches the DOM element in alocal cache, such as a cache in memory 206) for later retrieval inresponse to identifying the DOM element of the DOM tree structure thatcorresponds to the user's element of interest on the web page. In thecourse of future browsing, the user may return to the same web pagewhere the user has already expressed an interest in an element(s) onthat web page as discussed below in connection with FIG. 5.

FIG. 5 is a flowchart of a method 500 for retrieving a web page, wherethe user had previously expressed an interest in an element(s) on thatweb page in accordance with an embodiment of the present invention.

Referring to FIG. 5, in conjunction with FIGS. 1-3, in step 501, thebrowser of client device 101 receives a request to retrieve a web pagethe user had previously expressed a preference. That is, the browser ofclient device 101 receives a request to retrieve a web page, where theuser had previously expressed an interest in an element(s) on that webpage.

In step 502, the browser of client device 101 retrieves the stored DOMelement(s) that correspond to the element(s) in the web page the userhad previously expressed an interest. As discussed above, the browser ofclient device 101 stores the DOM element (e.g., caches the DOM elementin a local cache, such as a cache in memory 206) for later retrieval instep 405 of method 400 (FIG. 4) in response to identifying the DOMelement of the DOM tree structure that corresponds to the user's elementof interest on the web page.

In step 503, the browser of client device 101 transmits the request toretrieve the web page along with the stored DOM element(s) thatcorrespond to the element(s) in the web page the user had previouslyexpressed an interest to server 102.

In step 504, server 102 transmits the data (e.g., dynamic data, such asa YouTube® video) to populate the content of the received DOM element aswell as transmits the data to populate the content of the children ofthe received DOM element(s) to client device 101.

In step 505, server 102 transmits the data to populate the content ofthe remaining elements of the requested web page asynchronously to therequesting client device 101. That is, server 102 transmits the data topopulate the content of the remaining DOM elements (and their children)of the DOM tree structure asynchronously to the requesting client device101 for the requested web page.

In some implementations, method 500 may include other and/or additionalsteps that, for clarity, are not depicted. Further, in someimplementations, method 500 may be executed in a different orderpresented and that the order presented in the discussion of FIG. 5 isillustrative. Additionally, in some implementations, certain steps inmethod 500 may be executed in a substantially simultaneous manner or maybe omitted.

As previously discussed in connection with FIG. 4, the user may providefeedback concerning an element of interest in the requested web pageafter the element of interest is displayed on display 215 of clientdevice 101. However, the user may also concurrently express anelement(s) of interest along with the request to retrieve a web page asdiscussed below in connection with FIG. 6.

FIG. 6 is a flowchart of a method 600 for retrieving a web page when theuser concurrently expresses an element(s) of interest along with therequest to retrieve a web page in accordance with an embodiment of thepresent invention.

Referring to FIG. 6, in conjunction with FIGS. 1-3, in step 601, thebrowser of client device 101 receives a request to retrieve a web pagealong with an indication from the user of an interest in a DOMelement(s).

In step 602, the browser of client device 101 transmits the request toretrieve the web page along with the user specified DOM element(s) ofinterest to server 102.

In step 603, server 102 transmits the data to populate the content ofthe DOM element(s) of interest as well as transmits the data to populatethe content of the children of the DOM element(s) of interest to clientdevice 101.

In step 604, server 102 transmits the data to populate the content ofthe remaining elements of the requested web page asynchronously to therequesting client device 101. That is, server 102 transmits the data topopulate the content of the remaining DOM elements (and their children)of the DOM tree structure asynchronously to the requesting client device101 for the requested web page.

In step 605, server 102 updates a list of elements for the requestingweb page that is sorted in terms of popularity based on the received DOMelements corresponding to the user's elements of interest on the webpage. That is, server 102 updates a list that reflects the mostrequested web page elements for that web page.

In some implementations, method 600 may include other and/or additionalsteps that, for clarity, are not depicted. Further, in someimplementations, method 600 may be executed in a different orderpresented and that the order presented in the discussion of FIG. 6 isillustrative. Additionally, in some implementations, certain steps inmethod 600 may be executed in a substantially simultaneous manner or maybe omitted.

Upon establishing a list that reflects the most requested web pageelements for that web page, server 102 may appropriately respond withtransmitting to the browser of client device 101 the data to populatethe content of elements of higher interest prior to the elements oflower interest in the requested web page to be loaded by the browserthereby optimizing the loading of the web page (i.e., possibly reducingthe waiting time for the user to view the element(s) of interest in therequested web page) as discussed below in connection with FIG. 7.

FIG. 7 is a flowchart of a method 700 for retrieving a web page when theuser does not express an element of interest for the requested web pagein accordance with an embodiment of the present invention.

Referring to FIG. 7, in conjunction with FIGS. 1-3, in step 701, server102 receives a request to retrieve a web page with no element of the webpage specified as being important from client device 101.

In step 702, server 102 accesses the list of web page elements for therequested web page that is sorted in terms of popularity of the web pageelements for the requested web page.

In step 703, server 102 transmits the data to populate the content ofthe elements of the requested web page to client device 101 in an orderbased on the sorted listed. In this manner, server 102 transmits toclient device 101 the data to populate the content of the elements ofhigher interest prior to the elements of lower interest in the requestedweb page thereby optimizing the loading of the web page (i.e., possiblyreducing the waiting time for the user to view the element(s) ofinterest in the requested web page).

In some implementations, method 700 may include other and/or additionalsteps that, for clarity, are not depicted. Further, in someimplementations, method 700 may be executed in a different orderpresented and that the order presented in the discussion of FIG. 7 isillustrative. Additionally, in some implementations, certain steps inmethod 700 may be executed in a substantially simultaneous manner or maybe omitted.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

1. A method for optimizing the loading of a web page, the methodcomprising: receiving a request to retrieve a web page from a computingdevice of a user; accessing a list of web page elements for saidrequested web page that is sorted in terms of popularity; andtransmitting data to said computing device of said user to populatecontent of said web page elements of said requested web page in an orderbased on said sorted list.
 2. The method as recited in claim 1, whereinsaid request is a request to retrieve said web page with no element ofsaid web page specified as being important.
 3. The method as recited inclaim 1 further comprising: receiving indications of web page elementsof interest of said web page from a plurality of client devices; andforming said list of web page elements of said web page sorted in termsof popularity based on said received indications of web page elements ofinterest of said web page.
 4. The method as recited in claim 3, whereinsaid indications of web page elements of interest of said web page areexpressed as Document Object Model (DOM) elements.
 5. The method asrecited in claim 3, wherein an indication of a web page element ofinterest of said web page is identified in response to a user selectionof an area on said web page.
 6. The method as recited in claim 5,wherein said user selection comprises drawing an outline around said webpage element of interest on said web page.
 7. The method as recited inclaim 1 further comprising: receiving said request to retrieve said webpage along with one or more stored DOM elements that correspond to oneor more elements on said web page a user had previously expressed aninterest; and transmitting data to said computing device of said user topopulate content of said received one or more DOM elements as well astransmitting data to said computing device of said user to populatecontent of children of said received one or more DOM elements.
 8. Themethod as recited in claim 7 further comprising: transmitting data tosaid computing device of said user to populate content of remainingelements of said requested web page asynchronously.
 9. The method asrecited in claim 1 further comprising: receiving said request toretrieve said web page along with an indication from said user of aninterest in one or more DOM elements; and transmitting data to saidcomputing device of said user to populate content of said one or moreDOM elements of interest as well as transmitting to said computingdevice of said user to populate children of said one or more DOMelements of interest.
 10. The method as recited in claim 9 furthercomprising: updating said list of elements for said requesting web pagethat is sorted in terms of popularity based on said received one or moreDOM elements.